Repository navigation
Purge the whole cache, report the cache tags not written - #431
Merged
Merged
Conversation
The purge deleted the versions while reading the next pages of their list, which the deletions shift: a version of the cache was left after the purge of the main repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the purge of the layers cache, and reports the cache tags that a run did not write.
so some versions were never listed nor deleted (one remained after the first purge of
thecodingmachine/php-cache).It now reads the whole list first, then deletes it, and prints the number of versions deleted.
v5this morning did not write 6 and 9 cache tags of slim images, without any error in thejob: the cache export ignores its errors and the build was quiet. The build now writes its full output in
build.log, kept 7 days as an artifact of the job, and the runs ofv5show a warning listing the cache tags notwritten. The published images were not affected: the next run rebuilds these targets and writes their cache.
The build log holds the output of the build steps, as the run of a pull request: no secret is passed to the build,
the registry logins only appear as
[auth] … token for ghcr.iosteps, without the token.Test plan (required)
the new one deleted all of them. On this repository, it deleted the 202 versions of the cache.
v5) wrote the161 cache tags: the missing tags were not reproduced.
expected tag (reported).
Checklist